SUPPORT / SAMPLES & SAS NOTES
Problem Note 65512: Running a SYSTASK command results in an "Access is denied" message in the SAS® log
 |  |  |  |  |
Running a SYSTASK command results in an “Access is denied” message as well as a “Could not create a new process” error.
This problem occurs when all of the following conditions are true:
- You enabled both Integrated Windows authentication (IWA) and Kerberos constrained delegation.
- You are also running a SAS® Object Spawner under a domain account.
The problem does not occur when the SAS Object Spawner is running under the LocalSystem account
The workaround is to edit the WorkspaceServer_usermods.bat file in SAS\SAS-configuration-directory\Lev1\SASApp\WorkspaceServer\. In the file, add -limitui to the USERMODS_OPTIONS line. Save the BAT file, and then invoke the SAS® Workspace Server.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | Base SAS | Microsoft Windows Server 2012 Datacenter | 9.4_M6 | 9.4_M7 | 9.4 TS1M6 | 9.4 TS1M7 |
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M6 | 9.4_M7 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 R2 Std | 9.4_M6 | 9.4_M7 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 Std | 9.4_M6 | 9.4_M7 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2016 | 9.4_M6 | 9.4_M7 | 9.4 TS1M6 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2019 | 9.4_M6 | 9.4_M7 | 9.4 TS1M6 | 9.4 TS1M7 | ||